An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, I've been trying the last week trying to get my app approved for the App Store. It's my first app and I'm not really sure what's going on. My app is getting rejected due to "App Completeness". Here's the rejection message: App Review Guideline Issue This is an automated message. The review of this submission cannot proceed. See below for more information. The app crashed after the initial launch. Apps that crash negatively impact users. Test the app on supported devices to identify and resolve crashes and stability issues before resubmitting for review. Learn more about testing a release build. When we submitted the first time we got rejected because our Apple sign in did not auto fill the user's name and we didn't have the EULA Link in the description. So the app didn't crash here as a tester sent screenshots and was in our app. We resubmitted and then we started getting these crashes. I examined the code we added from the first revision and tested the start up and everything worked fine on ours and our 30+ beta testers end. The thing is we're not getting a crash log from Apple testers or Apple's automated tester (if automated testing exists?). We are creating a fitness app that implements HealthKit. We have the required HealthShare and HealthUpdate messages in the signing and capabilities of our target. I'm not sure this would be the issue since the app actually executed the first run though. I've researched and some articles did say long load times on bad internet could make iOS terminate an app. So we worked to get our initial load network calls down from 10 seconds to about 1-2 seconds. This did not work either. We are using SwiftData to cache exercises fetched from our backend locally but we haven't made any changes to the entity's. So I wouldn't expect bad data to cause a crash especially because we flush even if it were bad data anyway. I've ran with instruments to see if this was a memory issue: With an Authed User with data loaded it gets to about 33MiB With a fresh install memory usage is about 17MiB I did have a point of interest in my profile: api.revenuecat.com is not listed in your app’s NSPrivacyTrackingDomain key in any privacy manifest. It may be following users across multiple apps and websites to create a profile about users of apps that contact this domain. I don't use revenue cat for tracking for Ads so I probably shouldn't add it to the NSPrivacyTrackingDomain right? I'm really lost here any advice would be much appreciated. I guess my questions are if Apple has an automating testing environment how can I closely match that for testing on my end? If this is an actual tester why am I not getting a crash log or steps to repeat this issue? Has anyone else experienced the pain I'm currently suffering?

Our app update has been stuck in “Waiting for Review” for more than 8 days, and it appears the submission may have been overlooked or affected by a system issue on Apple's system. App ID: 1600450223 Bundle ID: com.asbing.woomanager Version: 5.3.1 What we’ve already tried: Requested an Expedited App Review Contacted Developer/App Review Support, but received no response (Case ID: 102878632497) Cancelled and resubmitted the update, but it remains in “Waiting for Review” for several days Could you please confirm whether this update is still in the review queue or if any issues are blocking the review? This is a critical release for us, and despite multiple attempts, we have been unable to resolve the issue.

Hello App Review Team, I’m reaching out regarding my first app release, Smala. App ID: 6762228514 Bundle ID: SmalaApp.Smala The app has now remained in Waiting for Review status for 8 days. I also submitted an expedited review request, which was approved, but the status has still not changed. This delay is creating significant launch issues for our team, as this release is time-sensitive. We would sincerely appreciate any assistance or status update when possible. Thank you very much for your time.

Hello Apple Developer Community, We are very excited to release our first apps on the App Store. I wanted to kindly ask for guidance because our first submissions appear to be taking longer than expected, and we want to make sure there is nothing missing or blocking the review process from our side. Our first app has been waiting for more than 15 days in total. App ID: 6761379839 Latest Submission ID: 8e767ece-a348-469a-9230-7e695e84ca44 After we first submitted the app, it entered review on the first day. App Review then requested a screen recording / walkthrough video. We prepared and submitted the requested screen recording immediately. After that, the submission did not appear to move forward for an extended period. While waiting, we continued development and completed a newer version of the app. Since the older submission had not progressed, we removed the previous build and submitted the newer version with an updated screen recording. One thing we noticed is that the subscription and in-app purchase products for this app appear to be “In Review.” We are not sure if this is expected behavior because the app version itself still appears to be waiting, or if there may be some kind of dependency or review state issue causing the submission to remain stuck. We also contacted Apple Developer Support regarding this situation. Case ID: 102882849875 We have another app on the same account that is also waiting for review. App ID: 6762281533 Submission ID: 0e4b607e-9e28-4d13-9c2a-98afe8c2e9aa This second app has been waiting for around 3 days. Could someone please advise or help us. Thank you very much.

Hi everyone, I recently submitted my app for review and it has been in the “In Review” status for more than 24 hours now. From my past experience, reviews were usually much faster, so I’m starting to wonder if this is still within the normal timeframe. There haven’t been any rejection messages or requests for additional information so far — it’s just been sitting in review. Is this something you’ve experienced recently? Are review times currently longer than usual? Any insights or shared experiences would be really helpful. Thanks in advance!

We are developing a non-custodial cryptocurrency wallet app with the following characteristics: Architecture: Users hold their own private keys at all times (we never custody any assets). The app includes identity credential verification: KYC-verified identity data (Verifiable Credentials / DID-based) is exchanged between the payer's iPhone and a counterparty device for identity verification purposes. NFCTagReaderSession is used only to exchange identity credential data via our proprietary, non-payment ISO 7816 AID with the counterparty device. Cryptocurrency transactions are submitted entirely over the internet (blockchain RPC), completely independent of the NFC session. NFC is NOT used to: Transmit cryptocurrency or payment instructions. Interact with any EMV payment AID or Secure Element. Replace or emulate Apple Pay or any payment card. Jurisdiction & licensing context: The app is being developed by a Japanese company for initial launch in Japan. While this question is posted from an individual Developer account for inquiry purposes, the app itself will be submitted under an appropriate Organization Developer account of the operating company, in compliance with Guideline 3.1.5(a)(ii). We are working with Japanese legal counsel to obtain any applicable Japanese financial-services license (e.g., 電子決済手段・暗号資産サービス仲介業 / Electronic Payment Instruments and Crypto-Asset Service Intermediary Business under the 2023-amended 資金決済法 / Payment Services Act) prior to App Store submission, and a written legal opinion will accompany the submission. We are not seeking to qualify as a 暗号資産交換業 (crypto-asset exchange) or 資金移動業 (funds transfer service operator), as our non-custodial design is intended to fall outside those categories under Japanese law. Question: Under Guideline 3.1.5, does a non-custodial wallet that uses NFCTagReaderSession solely for identity credential data exchange (not for transmitting cryptocurrency or payment instructions over NFC) fall under the "Wallets" sub-category — requiring an Organization Developer account only — or does NFC involvement for identity verification shift it toward a sub-category requiring additional licensing, entitlements, or financial institution credentials?

Hello App Review Team, Kindly assist with a response to the message sent on app submission. For the review team drop a message on the message trail and we responded but no feedback has been shared. Our submission ID - 8b32ad4d-9912-4f25-837c-13b15323a258. Thank you very much for your time and assistance.

Hello App review Team, Our app have been stuck in awaiting review since April 20th 2026 and no feedback. The submission ID - 8b32ad4d-9912-4f25-837c-13b15323a258, Is there a reason for this long waiting.When can we expect the review to proceed? Thank you very much for your time and assistance.

Hello, I’m reaching out regarding a critical delay in the app review process for App ID: 6743190232.😭😭😭😭 Despite submitting for review several days ago, the status remains unchanged. We have upcoming time-sensitive events tied to this release, and the current delay is causing significant disruption to our roadmap. I have already initiated a support ticket (Case No. 102878799248) and requested an expedite, but I have not received any feedback so far. I would deeply appreciate any assistance in moving this forward or providing a status update so we can plan accordingly.

Hello, My first app, Dodge? (Apple ID: 6757125102), has been in review for over 53 days. This app was already live on the App Store, and this submission only includes UI improvements. Additionally, my second app, Widgety – Desktop Widgets (Apple ID: 6761670888), has been in review for 13 days. This is my first time submitting this app for review. I have already contacted Apple support regarding this issue, but have not received a resolution so far, which is why I am posting here in the forums. Both apps have been pending for an unusually long time. Since Dodge? is just a UI update and Widgety is a standard first-time submission, I would expect a much faster review process. Could you please check the status of these submissions and let me know if any additional information or action is required from my side? Has anyone experienced similar delays or knows what might be causing this? Thank you.

Hi all, We are developing an iOS app that includes private user-to-user chats, commercial offer details with monetary value, and customer identification data. In line with OWASP MASVS-PLATFORM-3 requirements regarding unintentional sensitive data exposure, we need to protect these specific screens from screenshots and screen recording. We have carefully reviewed the relevant App Review Guidelines (2.5.1 on public APIs, 2.5.2 on self-contained bundles, 5.1.1 on privacy) and the related Human Interface Guidelines. From this analysis we have observed the following: iOS does not expose a public API to globally disable screen capture (no direct equivalent of Android's FLAG_SECURE). The SwiftUI .privacySensitive() modifier is effective for Lock Screen widgets and Always-On Display, but it does not appear to prevent screenshots or screen recording of an app's main UI while in the foreground. A number of widely distributed App Store apps (banking, authenticator, secure messaging) implement some form of screenshot protection on sensitive screens. Several established open-source libraries leverage the system behavior of UITextField with isSecureTextEntry as a wrapping container for arbitrary views, in order to achieve pixel-level protection for sensitive content. We would appreciate clarification on the following points: For privacy-driven protection of sensitive screens (private chats, customer data, monetized offers), is there an officially recommended approach we may have missed? Are there public APIs intended specifically for this use case beyond .privacySensitive()? Is the practice of leveraging UITextField with isSecureTextEntry as a wrapping container for arbitrary views considered an acceptable use of public APIs under Guideline 2.5.1, or does it carry App Review risk? Are there official recommendations or documentation for apps handling sensitive personal data that wish to align with industry standards such as OWASP MASVS-PLATFORM-3 for screenshot and screen recording leakage prevention? The intended use is strictly limited to a small number of screens marked as containing sensitive data (private messages, deal details, customer information). The protection would be selective and clearly communicated to the user via in-app messaging, not global to the app. Thanks in advance for any clarification, including pointers to existing documentation or threads we may have missed. Deployment target: iOS 15+

It takes forever to check the app! Hello everyone, I’m experiencing a very long delay with App Review and I’m not sure what else I can do at this point. I submitted my app for review about two weeks ago and it stayed in the “Waiting for Review” status the entire time. After waiting almost two weeks, I decided to cancel the submission and submit a new build, hoping it might help restart the process. Unfortunately, it has now been another week, and the app is still stuck in “Waiting for Review.” I have also contacted Apple Developer Support, but so far I have only received generic responses and no clear explanation or solution. I understand that review times can vary, but waiting several weeks without any real update is very frustrating, especially when I don’t know whether there is an issue with my submission or if I simply need to keep waiting. My app ID is: 6761535196 Has anyone experienced a similar situation recently? Is there anything else I can do to move the review forward or get more specific information from Apple? Any advice would be appreciated. Thank you.

Please help review app stuck 'Waiting for review'. Let me know if you need anything from us id: 6756242440

My app submitted on the 28th has been stuck in "Waiting for Review" for over 48 hours now. I even submitted an expedited review request more than 30 hours ago, and I’ve sent two follow-up inquiries, but I haven't received a single response yet. Is the review process broken at the moment? I’ve seen quite a few posts here recently about similar delays. If a problem occurs in the review process, the App Store must promptly make an announcement.

After going through 3 rejection rounds and addressing every piece of feedback from Apple, my app has been sitting In Review since April 22 with no movement. I've resolved all the issues raised and the submission was accepted into review, but that's where it stopped. I reached out to Developer Support several days ago and haven't received any response. Has anyone been in a similar situation, multiple rejections resolved, then silence during review? Is there a better escalation path than the standard support email? Any advice appreciated, it's tough to plan a launch when you're flying blind.

Hello everyone, I submitted my app to App Store Connect on March 27, 2026. As of today (April 30, 2026), the app is still in the “Waiting for Review” status. I have already contacted Apple Developer Support twice and received responses on April 15 and April 21. Both times I was told that the app is still in the queue and that there are no actions I can take to speed up the process. However, it has now been over a month, and I’ve noticed that many new apps and updates have been approved and released during this time. My app has not received any rejections or feedback—it’s still on its first submission and remains in “Waiting for Review.” I would appreciate any insights from others who may have experienced a similar delay: Is this kind of waiting time normal? Could there be any hidden issue causing the delay? Is there anything else I can do to move the process forward? Thank you in advance for your help.

My app submitted on the 28th has been stuck in "Waiting for Review" for over 48 hours now. I even submitted an expedited review request more than 30 hours ago, and I’ve sent two follow-up inquiries, but I haven't received a single response yet. Is the review process broken at the moment? I’ve seen quite a few posts here recently about similar delays. Is anyone else experiencing this kind of total silence from the review team? This is incredibly frustrating.

Hi, I can sign in to my Apple ID, but my Apple Developer account shows a “closed” status and I’m unable to access App Store Connect features. My app is currently showing “Ready for Distribution,” so the account appears active, but developer access is restricted. I’ve already contacted Apple Developer Support and am waiting for their response. Also, I temporarily can’t access my primary email due to a verification issue, so I’ve provided an alternate contact email and phone number in my support request. Has anyone experienced a similar situation or knows possible reasons for a “closed” developer status while the app remains approved? Thanks.

Hello everyone, I submitted my app to App Store Connect on March 27, 2026. As of today (April 30, 2026), the app is still in the “Waiting for Review” status. I have already contacted Apple Developer Support twice and received responses on April 15 and April 21. Both times I was told that the app is still in the queue and that there are no actions I can take to speed up the process. However, it has now been over a month, and I’ve noticed that many new apps and updates have been approved and released during this time. My app has not received any rejections or feedback—it’s still on its first submission and remains in “Waiting for Review.” I would appreciate any insights from others who may have experienced a similar delay: Is this kind of waiting time normal? Could there be any hidden issue causing the delay? Is there anything else I can do to move the process forward? Thank you in advance for your help.

Hello, My app Wecheerup 360 Booth (App ID: 676214516, bundle ID: com.wecheerup.wecheerup360booth.ios) has been stuck in the App Review process for longer than expected. Version 1.0.3 was submitted on April 13, 2026 and has been in “In Review” status for over 15 days. There are no messages in the Resolution Center and all metadata appears to be complete on my side.